Integration of a medicament delivery device with a smartwatch and a vehicle infotainment system

ABSTRACT

The exemplary embodiments may provide a smartwatch or a vehicle infotainment system with management and data inspection capabilities for a medicament delivery system. A user may view medicament delivery history and analyte level history via the smartwatch or auto mobile infotainment system. In addition, a user may calculate a medicament dosage and prompt delivery of the medicament bolus dosage via the smartwatch or vehicle infotainment system. Notifications also may be delivered to the user via the smartwatch and vehicle infotainment system.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 63/127,218, filed Dec. 18, 2020, and U.S. ProvisionalPatent Application No. 63/228,415, filed Aug. 2, 2021, the contents ofwhich are incorporated herein by reference in their entirety.

BACKGROUND

Medicament delivery devices, like insulin delivery devices, may haveassociated management devices. The management devices may be dedicatedhandheld electronic devices or may be smartphones or other mobileelectronic devices, upon which software for managing the medicamentdelivery device is installed. Each management device may provideinformation to a user, such as medicament delivery history and usermetrics, like glucose level history. The management device may alsoenable the user to control medicament deliveries. For example, the usermay be able to cause the delivery of a medicament bolus using amanagement device. Further, a user may be able set the dosage formedicament deliveries, such as basal medicament deliveries that aredelivered on an ongoing basis at periodic intervals, via the managementdevice.

Such a management device may be cumbersome. The user must carry themanagement device everywhere. In addition, the management device is notalways available for use as there are limitations as to where and when auser may use such a management device. For example, if a user is drivinga car, the user cannot easily use the management device, and using themanagement device while driving poses a driving safety hazard.

SUMMARY

In accordance with a first inventive aspect, a method is performed by aprocessor of a smartwatch. Per the method, a user interface element isdisplayed on a display of the smartwatch to request a bolus ofmedicament from a medicament delivery device. It is determined that theuser interface element has been used to request a bolus of medicament bedelivered to a user of the medicament delivery device, and responsive tothe determining, the medicament delivery device is instructed to deliverthe medicament bolus to the user.

The medicament may include at least one of insulin, a glucagon-likepeptide-1 (GLP-1) agonist, or pramlintide, for example. The method mayfurther include determining a dosage of the bolus of medicament for theuser. The determining of the dosage may comprise displaying a prompt onthe display of the smartwatch to obtain information for thedetermination of the dosage. The prompt may request a carbohydratesquantity. The method may further include displaying a reminder of when,and in some instances what (or a quantity of carbohydrates), the usershould eat on the display of the smartwatch.

In accordance with another inventive aspect, a method is performed by aprocessor of a smartwatch having a display. The method includesobtaining measured analyte history and medicament delivery history forthe user and displaying on the display at least one of an indication ofhistorical measured analyte values from the measured analyte historyand/or information about medicament deliveries in the medicamentdelivery history.

The medicament may be insulin, and the measured analyte values may beglucose concentration values. The method may further include displayinga user interface element on the display for accessing informationregarding a party under care of the user. The method may further includedetecting motion by the user and in response, displaying an option forthe user to change a mode of operation to protect the user.

In accordance with a further inventive aspect, a method is performed bya processor of a vehicle infotainment system. The method includesdisplaying a user interface element on a display of a vehicleinfotainment system to request a bolus of medicament from a medicamentdelivery device. The method further includes determining that the userinterface element has been used to request a bolus of medicament bedelivered to a user of the medicament delivery device and responsive tothe determining, instructing the medicament delivery device to deliverthe medicament bolus to the user.

The medicament may include at least one of insulin, a glucagon-likepeptide-1 (GLP-1) agonist, or pramlintide, for example. The method mayfurther include determining a dosage of the bolus of medicament for theuser. The determining of the dosage may comprise outputting a prompt toobtain information for the determination of the dosage. The prompt mayrequest a carbohydrates quantity. The user may provide a spoken responseto the prompt.

In accordance with an additional inventive aspect, a method is performedby a processor of a vehicle infotainment system having a display. Themethod includes obtaining measured analyte history and medicamentdelivery history for the user and displaying on the display of thevehicle infotainment system at least one of an indication of historicalmeasured analyte values from the measured analyte history and/orinformation about medicament deliveries in the medicament deliveryhistory.

The medicament may be insulin and the measured analyte values may beglucose level values. The method may further include outputting alarms,alerts or notifications to the user via the vehicle infotainment system.The outputting may entail outputting the alarms, alerts or notificationsby displaying information on the display of the vehicle infotainmentsystem and/or by generating audio output.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of a medicament delivery system suitablefor practicing the exemplary embodiments.

FIG. 2 depicts an illustrative home screen of a smartwatch of exemplaryembodiments.

FIG. 3 depicts a table for explaining illustrative trend icons that maybe used in exemplary embodiments.

FIG. 4 depicts illustrative views of glucose viewing screens for varyingtime intervals on a smartwatch in exemplary embodiments.

FIG. 5 depicts a flowchart showing illustrative steps that may beperformed in exemplary embodiments to set glucose level thresholds.

FIG. 6A depicts an illustrative glucose level and bolus history screenon a smartwatch in exemplary embodiments.

FIG. 6B depicts an illustrative insights screen on a smartwatch inexemplary embodiments.

FIG. 7 depicts a flowchart of illustrative steps that may be performedto calculate time range values in exemplary embodiments.

FIG. 8 depicts a flowchart of illustrative steps that may be performedin exemplary embodiments to calculate percentages by type of insulindelivery.

FIGS. 9A and 9B depict illustrative screens that may be displayed toconfirm whether a user wishes to suspend insulin delivery due to anactivity in exemplary embodiments.

FIG. 10 depicts a flowchart of illustrative steps that may be performedin exemplary embodiments to identify an activity by the user and tosuspend insulin delivery in response.

FIG. 11 depicts an illustrative screen on a smartwatch in exemplaryembodiments for use by a caretaker.

FIG. 12 depicts an illustrative screen on a smartwatch in exemplaryembodiments for locating a management device.

FIGS. 13 and 14 depict a sequence of illustrative screens on asmartwatch in exemplary embodiments for delivering an insulin bolus.

FIG. 15 depicts a sequence of illustrative screens on a smartwatch inexemplary embodiments where a user specifies a meal size rather than acarbohydrate amount in requesting an insulin bolus.

FIG. 16 depicts a sequence of illustrative screens on a smartwatch inexemplary embodiments where a user wishes to schedule a medicament bolusdelivery.

FIG. 17 depicts a sequence of illustrative screens on a smartwatch inexemplary embodiments where a user accesses the snooze functionality.

FIG. 18 depicts a sequence of illustrative screens on a smartwatch inexemplary embodiments where a user deletes a scheduled medicament bolusdelivery.

FIG. 19 depicts an illustrative home screen for a vehicle infotainmentsystem in exemplary embodiments.

FIG. 20 depicts an illustrative screen on a vehicle infotainment systemdisplay of exemplary embodiments showing insulin and glucose levelinformation.

FIG. 21 depicts an illustrative glucose viewing screen on a vehicleinfotainment system display of exemplary embodiments.

FIG. 22 depicts an illustrative screen that requests a voice command ona vehicle infotainment system display of exemplary embodiments.

FIG. 23A depicts an illustrative notification on a vehicle infotainmentsystem display of exemplary embodiments.

FIG. 23B depicts an illustrative notification history shown on a vehicleinfotainment system display of exemplary embodiments.

FIG. 24 depicts an illustrative sequence of screens on a vehicleinfotainment system display of exemplary embodiments for navigatingamong screens using voice commands.

FIG. 25 depicts an illustrative sequence of screens on a vehicleinfotainment system display of exemplary embodiments for delivering abolus of insulin responsive to voice commands.

FIG. 26 depicts an illustrative screen from a voice assistant on avehicle infotainment system display of exemplary embodiments requestingconfirmation that the user is going to exercise and requesting whetherto enter an insulin delivery mode in response.

FIG. 27 depicts a flowchart of illustrative steps that may be performedto use geolocation information in exemplary embodiments to determinewhat action is taken.

DETAILED DESCRIPTION

The exemplary embodiments may overcome the above-described problemsencountered with conventional management devices for medicament deliverysystems. In some exemplary embodiments, the user may wear a smartwatchthat provides much of the functionality available with the managementdevice and may also provide additional functionality. With thesmartwatch, there is no need to carry a management device since thesmartwatch is strapped to the wrist of the user. The smartwatch isinobtrusive, and the user does not need to hold a management device inhis/her hand. The user is less likely to lose the smartwatch and is lesslikely to forget to bring their smartwatch with them than a managementdevice given that the smartwatch is secured to the user's wrist.

The exemplary embodiments may also provide management devicecapabilities in a vehicle infotainment system. Thus, the managementdevice capabilities are available to the user as the user drives. Theuser may be able to issue voice commands to the vehicle infotainmentsystem to manage the medicament delivery device, including transmittingcommands to, and receiving information from, the medicament deliverydevice. As a result, the user is not required to attempt to access themanagement device while driving. Instead, the user may issue voicecommands that are received by the vehicle infotainment system and passedon to the medicament delivery device in a hands-free fashion. Anyinformation that is displayed may be displayed on the vehicleinfotainment system display, which is in the field of view of the user.

The term “vehicle infotainment system” may refer to an informationsystem, an entertainment system or both. Examples of an informationsystem include a navigation system that includes a display, a videodisplay that displays vehicle information, an onboard integratedcomputing device, etc. An entertainment system may include a radiosystem, a compact disk system, a video entertainment device like a DVDplayer, an integrated on-board gaming system, a streaming device forstreaming video or audio content, etc. The infotainment system mayinclude output display devices, like video displays, touchscreen displaydevices, a microphone, etc.

FIG. 1 depicts an illustrative medicament delivery system 100 that issuitable for delivering a medicament, such as insulin, a GLP-1 agonistor other medicament, like those detailed below, to a user 108 inaccordance with exemplary embodiments. The medicament delivery system100 includes a medicament delivery device 102. The medicament deliverydevice 102 may be a wearable device that is worn on the body of the user108. The medicament delivery device 102 may be directly coupled to auser (e.g., directly attached to a body part and/or skin of the user 108via an adhesive or the like) or connected to the user via tubing and aninfusion set. In an example, a surface of the medicament delivery device102 may include an adhesive to facilitate attachment to the user 108.

The medicament delivery device 102 may include a processor 110. Theprocessor 110 may, for example, be a microprocessor, a logic circuit, afield programmable gate array (FPGA), an application specific integratedcircuit (ASIC) or a microcontroller coupled to a memory. The processor110 may maintain a date and time as well as other functions (e.g.,calculations or the like). The processor 110 may be operable to executea control application 116 stored in the storage 114 that enables theprocessor 110 to implement a control system for controlling operation ofthe medicament delivery device 102. The control application 116 maycontrol medicament delivery to the user 108 as described herein. Thestorage 114 may hold histories 111 for a user, such as a history ofautomated basal medicament deliveries, a history of bolus medicamentdeliveries, meal event history, activity event history, sensor data,such as glucose level data obtained from a CGM, and the like. Inaddition, the processor 110 may be operable to receive data orinformation. The storage 114 may include both primary memory andsecondary memory. The storage 114 may include random access memory(RAM), read only memory (ROM), optical storage, magnetic storage,removable storage media, solid state storage, or the like.

The medicament delivery device 102 may include a reservoir 112 forstoring medicament for delivery to the user 108 as warranted. A fluidpath to the user 108 may be provided, and the medicament delivery device102 may expel the medicament from the reservoir 112 to deliver themedicament to the user 108 via the fluid path. The fluid path may, forexample, include tubing coupling the medicament delivery device 102 tothe user 108 (e.g., tubing coupling a cannula to the reservoir 112).

There may be one or more communications links with one or more devicesphysically separated from the medicament delivery device 102 including,for example, a management device 104 of the user and/or a caregiver ofthe user and/or sensor(s) 106. The communication links may include anywired or wireless communication link operating according to any knowncommunications protocol or standard, such as Bluetooth®, Wi-Fi, anear-field communication standard, a cellular standard, or any otherwireless protocol. The medicament delivery device 102 may also include auser interface 117, such as an integrated display device for displayinginformation to the user 108 and in some embodiments, receivinginformation from the user 108. The user interface 117 may include atouchscreen and/or one or more input devices, such as buttons, a knob ora keyboard.

The medicament delivery device 102 may interface with a network 122. Thenetwork 122 may include a local area network (LAN), a wide area network(WAN) or a combination therein. A computing device 126 may be interfacedwith the network, and the computing device 126 may communicate with themedicament delivery device 102.

The medicament delivery system 100 may include sensor(s) 106 for sensingthe levels of one or more analytes. The sensor(s) 106 may be coupled tothe user 108 by, for example, adhesive or the like and may provideinformation or data on one or more medical conditions and/or physicalattributes of the user 108. The sensor(s) 106 may, in some exemplaryembodiments provide periodic glucose concentration measurements and maybe a continuous glucose monitor (CGM), or another type of device orsensor that provides glucose measurements, such as glucoseconcentrations in interstitial fluid that accurately estimates bloodglucose levels. The sensor(s) 106 may be physically separate from themedicament delivery device 102 or may be an integrated componentthereof. The sensor(s) 106 may provide the processor 110 with dataindicative of one or more measured or detected analyte levels of theuser 108. The information or data provided by the sensor(s) 106 may beused to adjust medicament delivery operations of the medicament deliverydevice 102.

The medicament delivery system 100 may also include a management device104. In some embodiments, no management device 104 is needed; rather themedicament delivery device 102 may manage itself. The management device104 may be a special purpose device, such as a dedicated personaldiabetes manager (PDM) device. The management device 104 may be aprogrammed general-purpose device, such as any portable electronicdevice including, for example, a device with a dedicated controller,such as a processor, a micro-controller or the like. The managementdevice 104 may be used to program or adjust operation of the medicamentdelivery device 102 and/or the sensor 106. The management device 104 mayalso be used to view data and other information relating to medicamentdelivery and analyte levels. The management device 104 may be anyportable electronic device including, for example, a dedicated device, asmartphone, a smartwatch or a tablet. In the depicted example, themanagement device 104 may include a processor 119 and a storage 118. Theprocessor 119 may execute processes to manage and control the deliveryof the medicament to the user 108. The processor 119 may also beoperable to execute programming code stored in the storage 118. Forexample, the storage 118 may be operable to store a control application120 for execution by the processor 119. The control application 120 maybe responsible for controlling the medicament delivery device 102, e.g.,the automatic insulin delivery (AID) of insulin to the user 108. Thestorage 118 may store the control application 120, histories 121 likethose described above for the medicament delivery device 102 and otherdata and/or programs.

The management device 104 may include a user interface (UI) 123 forcommunicating with the user 108. The user interface 123 may include adisplay, such as a touchscreen, for displaying information. Thetouchscreen may also be used to receive input when it is a touch screen.The user interface 123 may also include input elements, such as akeyboard, button, knobs, or the like.

The management device 104 may interface with a network 124, such as aLAN or WAN or combination of such networks. The management device 104may communicate over network 124 with one or more servers or cloudservices 128.

The medicament delivery system 100 may include a smartwatch 130 worn bythe user 108. The smartwatch 130 includes a processor 140, like amicroprocessor, for executing computer programming instructions such asan application 148 for performing the functionality described herein.The smartwatch 130 also includes a display 142 for displaying content.The display 142 may be a touchscreen for receiving input as well. Thesmartwatch 130 may include audio output/input 144, such as a speaker anda microphone. The smartwatch 130 may include storage, such as describedabove for the management device 104, for holding data and software, likethe application 148.

The smartwatch 130 has a wireless communication connection with themanagement device 104. The smartwatch 130 may issue commands to themedicament delivery device 102 and obtain information from themedicament delivery device 102 by way of wireless communications sent tothe management device 104 over the connection. In some embodiments, thesmartwatch may have a direct communication link with the medicamentdelivery device 102 to obtain information and issue commands as shown inFIG. 1. In other embodiments, the smartwatch 130 may forward aninstruction to the management device 104, which then issues the commandto the medicament delivery device 102. Similarly, the smartwatch 130 mayrequest information. This request may be received by the managementdevice 104 and then forwarded to the medicament delivery device 102. Themedicament delivery device 102 provides the requested information to themanagement device 104, which returns the requested information to thesmartwatch 130. The functional capabilities of the smartwatch 130 inrelation to the medicament delivery system 100 will be described in moredetail below. The application 148 facilitates communications with themanagement device 104 and provides the functionality of the smartwatch130, which is described in more detail below.

A vehicle infotainment system 150 may be part of the medicament deliverysystem 100. The vehicle infotainment system 150 may be like those foundin many vehicles to enable a user to listen to the radio, play music orother audio content from a portable device like a smartphone, thumbdrive or the like. The vehicle infotainment system 150 may providenavigation assistance via displayed maps and audio output. The vehicleinfotainment system may include a processor, like a microprocessor,microcontroller or ASIC, for executing computer programminginstructions, such as application 158. The vehicle infotainment system150 includes a display 154, such as a touch screen display, and audiooutput/input 160, such as loudspeakers and a microphone. The vehicleinfotainment system 150 includes storage 156, which may comprise memorydevices like those discussed above relative to storage 114. The storage156 may store the application 158. The application 158 facilitatesfunctionality described herein. In some embodiments, the managementdevice 104 include an application and the vehicle infotainment system150 may communicate with the management device 104 to realize thefunctionality described herein.

The vehicle infotainment system 150 may issue commands to the medicamentdelivery device 102 and obtain information from the medicament deliverydevice 102 by way of wireless communications sent to the managementdevice 104 over the connection. Technologies, such as Apple CarPlay orAndroid Auto, may be used to integrate the management device 104 and thevehicle infotainment system 150. The vehicle infotainment system 150 mayforward an instruction to the management device 104, which then issuesthe command to the medicament delivery device 102. Similarly, thevehicle infotainment system 150 may request information. This request isreceived by the management device 104 and forwarded to the medicamentdelivery device 102. The medicament delivery device 102 provides therequested information to the management device 104, which returns therequested information to the vehicle infotainment system 150. Thefunctional capabilities of the vehicle infotainment system 150 inrelation to the medicament delivery system 100 will be described in moredetail below. The application 158 facilitates communications with themanagement device 104 and provides the functionality of the vehicleinfotainment system 150, which is described in more detail below. Insome alternative embodiments, the vehicle infotainment system 150 mayhave a direct wireless connection with the medicament delivery device102 as shown in FIG. 1 by the connecting lines.

As was mentioned above, the medicament delivery system 100 may include asmartwatch 130, such as the Apple® Watch, the Fitbit® Versa smartwatch,the Samsung® Galaxy watch, etc. The smartwatch 130 may execute theapplication 148 on the processor 142 to provide the functionalitydescribed herein. FIG. 2 depicts an example of an illustrativesmartwatch 200 that is suitable for use with exemplary embodiments. Inthis example, the smartwatch 200 is used to control the medicamentdelivery device 102 in the form of an insulin delivery device. Thesmartwatch 200 includes straps 202 for securing the smartwatch to thewrist of the user 108. The smartwatch 200 includes a display 204. Insome exemplary embodiments, the display 204 may be a touchscreendisplay. The smartwatch 200 may include a rotatable wheel 206. Therotatable wheel 206 may be used to cycle through a list of displayeditems as will be discussed below. The home screen shown in FIG. 2 maydisplay a current analyte level for the user. In FIG. 2, the analytelevel is the current glucose level reading 208 (“110”) for the user 108.The current glucose level reading may be obtained from the managementdevice 104 or the medicament delivery device 102 in some embodiments.The insulin on board (IOB) 210 is also displayed on the home screen(“1.05”). The home screen displays an icon 212 that may be selected torequest the delivery of an insulin bolus to the user 108. Another icon214 displays a trend icon for the analyte level. In this exemplary case,the analyte level is the glucose level of the user 108.

There are a variety of different trend icons other than the trend icon214 shown in FIG. 2 that may be displayed to provide a visual cue of thetrend of the analyte level of the user 108. FIG. 3 depicts a table 300showing a list of illustrative trend icons that may be displayed. Thetable 300 is organized by row. Row 302 depicts a sideways pointing arrowicon, which means that the glucose level of the user 108 is increasingor decreasing less than 1 mg/dL each minute. Row 304 depicts an upwardfacing arrow icon and a downward facing arrow icon that are eachoriented at 45°. These icons in row 304 indicate that the glucose levelof the user 108 is increasing (upward-oriented arrow icon) or decreasing(downward-oriented icon) at a rate of 30-60 mg/dL per 30 minutes. Row306 shows an upward facing arrow icon and a downward facing arrow icon.These icons indicate that the glucose level of the user 108 isincreasing or decreasing respectively at a rate of 60-90 mg/dL per 30minutes. Lastly, row 308 depicts an icon with two upward facing arrowsand an icon of two downward facing arrows. These icons indicate that theglucose level of the user 108 is increasing or decreasing at a rate ofmore than 90 mg/dL.

With reference to FIG. 2 again, a status view 216 specifies the insulindelivery mode as being a manual mode (open loop), limited mode whereconnectivity with a sensor is limited (such as when there is limitedconnectivity with a CGM, or when a connection with a CGM is currently inprogress) or an automated mode (hybrid closed loop) or any other modethat might need to be communicated to the user, such as a hypo-protectmode where insulin delivery to the user is reduced or stoppedtemporarily to protect against hypoglycemia. In the example depicted inFIG. 2, the status view indicates that the current insulin delivery modeis the automated insulin delivery mode.

The smartwatch 130 may provide information to the user 10 regardinganalyte level history and trends. FIG. 4 shows exemplary displays forthe case where the smartwatch 130 is used with an insulin deliverydevice. The user 108 may select the duration of the view shown on thedisplay 405 of the smartwatch 401. FIG. 4 shows a graph 411 for asix-hour view 402, a graph 412 for a three-hour view 404 and a graph 414for a one-hour view 406. It should be appreciated that these timeintervals are merely illustrative and are not intended to be limiting.Other time intervals may be used. Each graph 411, 412, and 414 showsglucose level values 410 over the specified time interval. These views402, 404, and 406 enable a user to understand the trend in the glucoselevel over respective time intervals. User-adjustable high or lowglucose concentration thresholds 408 are shown in each of the views 402,404, and 406. The most recent glucose concentration reading 403 isdisplayed along with the trend icon 407. The user for which the data isbeing displayed is identified by text 422 shown at the top of thedisplay 405. This is helpful for caretakers that may need to view thedata for another party or multiple parties. Graphical bar 416illustrates the period in which insulin delivery was suspended duringthe specified time interval. Icon 418 shows where during the timeinterval a bolus was delivered.

The user 108 may set the glucose concentration thresholds 408 asmentioned above. Specifically, as depicted in the flowchart 500 of FIG.5, the user 108 may set the upper glucose concentration threshold at502, and the user may set the lower glucose concentration threshold at504. Once these thresholds are set, the thresholds may be displayed onthe display of the smartwatch 130 with the glucose level history ingraphical form, such as shown in FIG. 4.

In the exemplary embodiments, the smartwatch 600 may show historicalglucose level and medicament bolus information on the display 602 asdepicted in FIG. 6A. The smartwatch 600 may, for instance, obtaininsulin delivery information 604, glucose level history and recentmedicament bolus delivery history from the management device 104 andthen display the information on the display 602. The displayedinformation 604 may include the time that the bolus delivery was made,the glucose level of the user 108 at the time of the bolus delivery andthe amount of the bolus delivery. The smartwatch 600 may show agraphical depiction 606 that indicates by color and magnitude the numberof recent glucose level readings that were above the target value range,below a target value range, or within the range. The percentage of therecent glucose level readings that are above the range 608 may bedisplayed along with the percentage of recent glucose readings that arebelow the range 612. The percentage of recent glucose level readingsthat are within range 610 may be displayed. The average of the recentglucose level readings 614 may also be displayed. The smartwatch 600 mayperform calculations that are needed to determine these percentagesprior to the display of the percentages.

The smartwatch 600 may also show insights regarding the insulindeliveries by the user and the total carbohydrates ingested by the userover a period of time. The insights are obtained by processing thegathered data regarding the user 108. FIG. 6B shows a display like thatof FIG. 6A but with information regarding the insights and the lastbolus delivery. The insights 620 includes a depiction 624 of the totalinsulin delivered for a time interval, such as a day or a past hour. Inthe depicted example case, the recent glucose level readings include tenreadings. The percentage of insulin deliveries that were basal insulindeliveries 626 is displayed along with a percentage of insulindeliveries that were bolus insulin deliveries 628. The totalcarbohydrates ingested during the time interval 630 is also displayed.The dosage and time of the last bolus delivery 622 is shown on thedisplay 602.

The time in range values that are displayed in the insights sectionshown in FIG. 6B need to be calculated by the application 148. FIG. 7depicts a flow chart 700 showing illustrative steps that may beperformed by exemplary embodiments to calculate the time in rangevalues. First, the application 148 must calculate the percentage ofglucose level values for the time interval that are in range at 702. Therange may be bounded by the threshold values that are set by the user.The application 148 determines how many of the values fall within thedefined range, and then determines what percentage of the total thosevalues constitute. The application 148 also calculates the percentage ofglucose level values for the time interval that are above the upperthreshold of the range at 704. This entails determining how many of thevalues are above the upper threshold of the range, dividing that numberof values by the total number of values, and converting the results to apercentage. At 706, the percentage of glucose level values for the timeinterval that are below the lower threshold of the range is determined.This entails determining how many values are below the lower thresholdof the range, dividing that number by the total number of values andconverting the result to a percentage.

FIG. 8 depicts a flowchart 800 of illustrative steps that may beperformed to determine a breakdown of insulin delivery to the user for atime interval by type of insulin delivery. Initially, at 802, theapplication 148 determines the total amount of insulin that has beendelivered to the user 108 for the time interval. This entails summingthe amounts of insulin delivered to the user 108 at basal rates for thetime interval and summing the amounts of bolus insulin delivered to theuser 108 for the time interval. The resulting sum constitutes the totalinsulin delivered for the time interval. The percentage of insulin thatis utilized for basal rates may be determined at 804 by dividing sum oftotal bolus insulin delivered for the time interval by the total amountof insulin that was delivered for the time interval. The percentage ofinsulin that is not bolus insulin is calculated at 806 by dividing thesum of the insulin that is delivered at basal rates for the timeinterval with the total insulin delivered for the time interval. A ratiomay be determined by dividing the bolus insulin by the total insulin(which may yield a value around 0.5). Alternative methods may be used todetermine this ration

The application 148 may exploit features provided by the smartwatch 900(FIG. 9A) to aid in controlling medicament delivery to the user 108 andfor interacting with the user 108. For example, the smartwatch maycontain an accelerometer that detects movement by the user 108. Thesmartwatch 900 may have intelligence, such as found in a fitnessapplication on the smartwatch 900 to match the detected activity by theaccelerometer with patterns of movement found with exercise, or eating,or driving in a car, for example. Alternatively, motions, like handmotions, may signal activities, like eating. FIG. 10 depicts a flowchart1000 of illustrative steps that may be performed in exemplaryembodiments to detect an activity, such as exercise, eating, or driving,and adjust medicament delivery accordingly. At 1002, the smartwatch 900detects activity that may be exercise (or eating, or driving, forexample) or signal an activity (e.g., through hand motions) via theaccelerometer. If the activity pattern matches that of exercise (orother activity), the smartwatch 900 may confirm with the user that theuser is exercising (or engaged in another activity) at 1004. FIG. 9Ashows an example of the user interface that may be displayed on thesmartwatch 900 in response to detecting activity that may be exercising.The display 902 contains a prompt 904 for asking the user 108 if theuser 108 is exercising. The prompt 904 may be combined with an audiblesound, a light emission, or a vibration, for example. The user 108 hasthe option of responding to the prompt 904 by selecting a “Yes” button906 or a “No” button 908. If the user 108 does not confirm theexercising, the processing may stop. If the user 108 confirms theexercising, the user 108 may be asked if the user 108 wants to take anaction that may benefit their insulin management, such as entering adifferent insulin management mode that may suspend delivery of insulin,at 1006. The suspension of insulin delivery is a precautionary measureto prevent the user 108 from becoming hypoglycemic during theexercising. The exercising reduces the glucose level of the user. Whencombined with an insulin delivery, the exercising may reduce the glucoselevel of the user more than desired. FIG. 9B depicts an illustrativeuser interface that may be shown on the display 902 of the smartwatch900. A prompt 910 asks the user 108 if the user would like totemporarily suspend insulin delivery. The user may select a “Yes” button912 or a “No” button 914 in response to the prompt 910. At 1008, a checkis made whether to suspend insulin delivery or not based upon whichbutton 912 or 914 the user chooses. If the user chooses the “Yes” button912, insulin delivery is suspended for an interval, such as 30 minutesor one hour. If the user chooses the “No” button 914, no furtheractivity regarding this suspension is taken.

As was mentioned above, the smartwatch 130 may be used by caretakersthat need to have access to information for those they are assisting andneed to be able to deliver medicament as needed for those the caretakersare assisting. To that end, as shown in FIG. 11, the smartwatch 1100 mayshow on its display 1102 a prompt 1104 that asks the caretaker whichuser they would like to view information regarding. In the example shownin FIG. 11, an icon and a textual name 1106 is shown for “Matt” and anicon in a textual name 1108 is shown for “Sarah”. The caretaker needsonly select one of the icons 1106 or 1108 to view information regardingthat user or for selecting an icon with their own name where the user isa caregiver as well as a patient.

Sometimes it is easy for a user to misplace a management device 104. Thesmartwatch 1200 (FIG. 12) provides an ability to help locate themanagement device 104. Specifically, the display 1202 of the smartwatch1200 may contain an icon 1206 and a prompt that when selected oractivated causes the management device 104 to produce an audio output,such as a ringing or beeping. This audio output helps the user 108 tolocate the management device 104. In this example, the management device104 is a personal diabetes manager (PDM).

The smartwatch 130 provides the ability to calculate an insulin bolussize and to deliver the insulin bolus of the specified size to the user108. The user 108 may initiate the process of calculating a bolus anddelivering an insulin bolus by selecting the option to deliver aninsulin bolus, such as by selecting icon 212 (FIG. 2). FIG. 13 shows asequence of screens that may be displayed on the display 1302 of thesmartwatch 1300 to facilitate calculation of an insulin bolus anddelivery of the insulin bolus to the user 108. The user 108 may beprompted initially to enter a glucose value. The user 108 may enter avalue in text box 1306 or may scroll through displayed value options1308 to select among displayed value options 1308, such as value 1310,using the rotating knob 1304. The glucose value may also beautomatically populated by a continuous glucose monitor (CGM) that ispaired with the insulin controller system. The entered glucose value maybe a glucose concentration value expressed in terms of mg/dL or mmol/L.The user 108 is then prompted to enter the amount of carbohydrates asshown in FIG. 13. The user may manually enter the grams of carbohydratesin text box 1312 or may scroll through options to select a value such asthe highlighted value 1314. In the next screen, the display 1302 of thesmartwatch 1300 shows the entered glucose concentration value 1316representing the most recent value for the user 108 and the amount ofcarbohydrates to be ingested in a meal 1318 that was entered by the user108. A correction factor 1320 is also displayed. The correction factoris the number/formula used to correct a user's high or low blood sugarthat is out of range. This is managed in his or her settings in thecontrol software. The correction factor indicates how much insulin isrequired to correct for a gram of carbohydrates ingested. The correctionbolus may be populated if a user's blood glucose level is out of rangeand needs to be factored into an execution of a bolus. This may be acorrection for a high blood glucose value by adding to the total bolusamount or a reverse correction for a low blood glucose value that wouldsubtract from the overall bolus value. The application 148 thencalculates using the provided information and correction factor anddisplays the appropriate correction bolus dosage to compensate for theindicated number of carbohydrates given the current glucoseconcentration (see 1322). In the example case, it will take 2.5 units ofinsulin to compensate for 25 grams of carbohydrates (i.e., 25×0.1). Theuser 108 may be prompted to confirm the formulation of the bolus byphysical action, such as swiping right, or verbal action, such asverbally confirming the bolus. In the next screen, the user 108 isprompted to select either option by selecting a normal bolus byselecting element 1326, or an extended bolus by selecting element 1328.In this example, the user 108 selects by swiping the element 1326 or1328 to the right. In the example of FIG. 13, the user 108 has selectedthe extended bolus as indicated by text at 1330 on display 1302. Theuser 108 enters percentage values to specify how the extended bolus isto be distributed over time. In text box 1332, the user 108 enters thepercentage of the bolus to be delivered now. In text box 1334 the user108 enters the percentage of the bolus to be delivered in an extendedfashion. In text box 1336, the user 108 enters the duration over whichthe extended portion is to be delivered. The smartwatch 130 may alsoprompt the user to review the insulin amount to be distributed ratherthan using percentages for extended boluses. Once the user 108 hasentered the appropriate values, the user 108 may confirm the extendedbolus delivery by selecting element 1338, such as by swiping to theright.

FIG. 14 shows a next sequence of screens after the user 108 has selectedto have an extended bolus delivered. The user 108 has initially selectedan extended bolus as shown in screen 1404 on display 1402. The user 108is then prompted 1414 to confirm delivery of the number of units asshown by display 1412. If the user accepts the delivery of the 2.5units, the user enters a confirmatory code via screen 1416 to initiatethe delivery. The confirmatory code may be established with the userduring user on-boarding. The smartwatch 1400 then displays the screen1418 on display 1402 to remind the user 108 that they will be notifiedwhen it is ok to eat. This time parameter will be set by the user 108 inthe insulin controller system application, whether that is a controlleror smartphone application. The goal of the mealtime reminder is toimprove user's pre-bolus activity by giving insulin before a meal inorder to stay in target glycemic range. In the example shown, the useris reminded to eat in 15 minutes. After the 15 minutes has elapsed, thesmartwatch 1400 displays a screen 1406 on display 1402 reminding theuser 108 that it is time for the user 108 to eat. This helps the user108 to avoid a problem by having the insulin bolus delivered withoutingesting the carbohydrates for which the insulin bolus is intended, inaddition to knowing ample time has passed for the user to ingest thecarbohydrates.

The smartwatch 130 may also enable the user to simply choose the size ofmeal that is to be ingested to determine the insulin bolus dosage ratherthan specifying the amount of carbohydrates to be ingested in grams. Theapplication 148 may have categories of meal sizes, such as a regularmeal and a large meal. A regular meal is presumed to include a firstamount of carbohydrates, whereas a large meal is presumed to include asecond amount of carbohydrates that is larger than the first amount. A“small meal” or “snack” may also be presented as an option, which maycorrespond to a lower amount of carbohydrates than the regular mealoption. These carbohydrate amounts may be defined by either the user 108or health care provider by programming such amounts into the insulincontroller system. Custom meal names (and carbohydrate amounts) may alsobe set up by the user in the insulin controller system. As shown in FIG.15, the smartwatch 1500 may show on display 1502 a regular meal option1504 and a large meal option 1506 for selection by the user 108. Theuser 108 may then be prompted to confirm which of the meal sizes theuser 108 selected in screen 1506. The screen 1506 may include a “Yes”button 1508 to confirm the selected meal size or a “No” button 1510 tonot confirm the selected meal size. If the user 108 confirms the mealsize by selecting the “Yes” button 1508, the user 108 is prompted toenter a confirmatory code to initiate the delivery of the insulin bolususing display 1512. The user 108 may also be prompted by a voice commandon the smartwatch 1500 to confirm the meal, by which the user 108 mayconfirm verbally. As was described previously above, screen 1514provides a reminder of when the user 108 should eat. This screen 1514 isfollowed by a follow up reminder screen 1516 when the time to eatarrives. Screen 1516 reminds the user 108 that it is time for the user108 to eat.

The user 108 may also schedule a drug delivery, such as a bolus ofinsulin, via the smartwatch 130. FIG. 16 depicts a screen 1600 on thesmartwatch 130 that provides the user 108 with options regarding bolusdelivery. A bolus now button 1602 may be selected, such as by touchingthe touchscreen of the smartwatch 130, to deliver the bolus immediately,such as described above. A schedule bolus button 1604 may be selected bythe user 108 to schedule a future date and time for the delivery of thebolus. A back button 1606 may be selected to navigate back to theprevious screen. If the user 108 selects the schedule now button, screen1610 may be displayed. The screen 1610 contains user interface elementsfor that facilitate scheduling of the medicament bolus delivery. Userinterface element 1616 enables the user 108 to enter or edit the bolusamount to be delivered. User interface elements 1618 may be used to bythe user to specify the month and day for the date of the scheduledmedicament bolus delivery. User interface elements 1620 may be used bythe user 108 to specify the time of the scheduled bolus delivery inhours and minutes. The confirm button 1624 may be selected by the user108 to confirm the bolus amount and the date and time of the scheduledmedicament bolus delivery. Upon the confirm button 1624 being selected,a confirmation screen 1630 may be displayed that shows the bolus amount1632, date 1634 and time 1636 for the scheduled bolus delivery.

The user 108 may then determine, by using the smartwatch controls, suchas a dial or a touchscreen user interface, the amount, the date and timewhen the application 148 will prompt a scheduled bolus reminder. Screen1700 in FIG. 17 depicts an illustrative scheduled bolus reminder. Screen1700 depicts the bolus amount 1701 that is scheduled to be delivered. Aconfirm button 1702 is provided for selection to confirm the scheduledbolus. If the user 108 selects the confirm button 1702, a number pad1710 may be displayed to enter a password or PIN as an additional layerof security.

A snooze button 1704 also is displayed. Selection of the snooze button1704 delays the scheduled bolus by a determined amount of time. When theuser 108 selects the snooze button 1704, screen 1712 may be displayed.The user 108 is presented with buttons 1716 that may be selected tochoose among the options for the magnitude of the snooze (e.g., 5, 10,15, 20, 25 or 30 minutes). The user 108 may effectuate the delay byselecting snooze button 1714.

When the user 108 selects the edit or cancel button 1706, screen 1718may be displayed. Screen 1718 includes an editable text box 1722 inwhich the user 108 may modify the bolus amount. User interface elements1724 enable the editing of the date for the scheduled bolus, and user108 interface elements 1726 enable the editing of the time of thescheduled bolus. After editing the bolus amount, date and/or time, theuser 108 may select button 1728 to confirm the modified particulars ofthe scheduled bolus delivery. If the user 108 wishes to cancel thescheduled bolus, the user 108 needs to only select the cancel button1730. If the user 108 confirms the edited scheduled bolus delivery,screen 1740 may be displayed to show the bolus amount 1742, thescheduled date 1746 and the scheduled time 1748 for the edited scheduledbolus delivery.

As shown in FIG. 18, a user 108 may view when multiple boluses arescheduled to be delivered in a list view. Screen 1800 may be displayed,for example. In this illustrative case, the information 1802 for a firstscheduled bolus is displayed, and information 1804 for a secondscheduled bolus is displayed. A button 1806 for scheduling a new bolusalso is displayed. When the displayed information 1804 for the secondscheduled bolus is selected by swiping left. Arrow icon 1812 isdisplayed to evidence the swipe. In addition, an edit button 1814 may bedisplayed to cause editing of the second scheduled bolus. A deletebutton 1816 is displayed for deleting the second scheduled bolus. Whenthe delete button 1816 is selected, a button 1822 may be displayed onscreen 1820 to confirm the deletion, and a cancel button 1824 may bedisplayed for canceling the deletion. If the user 108 selects the editbutton 1816, an edit screen 1830 is displayed. The edit screen 1830includes user interface elements 1831, 1832 and 1834 for editing thebolus amount, the date and time, respectively, of the second scheduledbolus. The edited particulars for the second scheduled bolus may beaccepted by selecting button 1836 or may be rejected by selecting button1838.

The user 108 may also use the vehicle infotainment system 150 whendriving or in a vehicle, such as a car, a truck, a motorcycle or anothertype of vehicle, to interact with the medicament delivery device 102 andthe management device 104. FIG. 19 depicts an example of the display1900 for the vehicle infotainment system 150. The display 1900 istypically positioned in the dash of the vehicle in the field of view ofthe driver. A group of icons 1902 are displayed for selection by theuser 108. Each icon is associated with a particular application. Icon1904 is for the application 158 that controls and interacts with themedicament delivery device 102. The user 108 may select the icon 1904via touch on the touchscreen display or by way of spoken command. Themanagement device 104 may support voice commands and the application 158may leverage that capability.

Once the icon 1902 has been selected, the home screen 2002, like thatshown in FIG. 20, may be displayed on display 2000 of the vehicleinfotainment system. The home screen includes a display 2004 of the lastglucose level reading and text 2006 specifying the time of the lastglucose reading. In addition, the home screen 2002 may display an arrowicon 2008 indicating the current trend in glucose level values for theuser 108. The home screen 2002 may display the insulin on board 2010 forthe user 108. The home screen 2002 may show a plot 2016 of glucose levelvalues for the user 108, which may be driven by a paired CGM sensor. Acurve 2024 of the values over a specified time interval is depicted inthe plot 2016. The user-selected lower threshold 2026 and upperthreshold 2028 are depicted in the plot 2016. As with the smartwatch130, the application 158 may obtain the data regarding glucose levelhistory and insulin delivery history from the management device 104 oreven from the medicament delivery device 102. A notifications icon 2020may be selected to display notifications that have been generated by themedicament delivery system 100. To use voice commands, the user 108 mayselect icon 2022 to activate the voice recognition agent.

If the user 108 wishes to view more information regarding the historyand trends of the glucose concentration values for the user 108, theuser 108 may select to view the glucose viewing screen. FIG. 21 depictsan illustrative glucose viewing screen 2102 shown on the display 2100.Three buttons 2104 are displayed to allow the user 108 to select whetherto view a one-hour view, a three-hour view or a six-hour view. In theexample shown in FIG. 21, the user 108 has selected the three-hour view.The user 108 may be able to adjust the viewing window options displayedon the application in the medicament device settings. A plot 2112 isdisplayed that includes a curve 2110 of the glucose level readings overthe three-hour interval. The lower threshold 2108 and the upperthreshold 2106 are displayed. The glucose viewing screen 2102 alsodisplays the most recent glucose level value 2118 and the trend icon2120. A home button 2116 is provided to return to the home screen. Abutton 2114 is provided to invoke the use of voice commands. When theuser selects the icon 2114, a screen 2202 like that shown in FIG. 22 isdisplayed on the display 2200. A prompt 2204 is provided to prompt theuser to provide voice commands.

As was mentioned above, the medicament delivery system 100 may generatealerts alarms and other notifications. These notifications may appear onthe display of the vehicle infotainment system in some embodiments. Thenotifications are generated by the application 158 or by the managementdevice 104. FIG. 23A depicts an example notification 2304 shown on thedisplay 2302 for the vehicle infotainment system 2300. The notification2304 contains textual content. In this example, the notification 2304informs the user 108 that the medicament delivery device has less than50 units of insulin remaining. Once the user 108 has read thenotification, the user 108 may dismiss the notification by selecting the“Dismiss” button 2306. The notification may also disappear after a settime period depending on the priority of the message.

The user 108 may also see a history of the most recent notifications.FIG. 23B depicts a display 2312 for the vehicle infotainment system 2300showing a history of notifications organized in list form inchronological order from most recent to oldest but may be sorted basedon user 108 preference in the medicament device. Each notificationincludes a time and a description of the notification. For example,notification 2310 was issued at 9 AM and informs the user 108 that themedicament delivery device expires in four hours. Notification 2308 wasissued at 9:25 AM and informs user 108 of the delivery of a bolus ofinsulin of 3.5 units. The term “Bolus” is highlighted to indicate a useror system action. The screen 2312 also includes a home button 2314 toreturn to the home screen.

The user 108 may use voice commands to navigate to the glucose viewingscreen and to make selections on that screen to operate hands free. Thisis helpful to a driver of a vehicle. A voice assistant may be providedas part of application 158 or the voice assistant of the managementdevice 104 may be used. FIG. 24 depicts a sequence of screens that maybe displayed in an illustrative instance. Initially, at step one, screen2400 is displayed to indicate that the voice commands have beenactivated. In this example the user asks for his/her most recent glucoselevel reading as indicated by 2402. The voice assistant generates screen2404 at step two to confirm receipt of the voice command. Next, the viewof the glucose viewing screen 2406 is displayed at step three. In theexample of FIG. 24, at step four, the user 108 may use the buttons toselect the time interval of the view, as has been discussed above. Instep five, as shown in screen 2410, a prompt that the voice assistant iswaiting for a voice command is displayed after the user has initiatedthe voice assistant by selecting the “Ask Omnipod” button on the system.The user 108 issues a voice command to go to the home screen asindicated by 2412. At step six, the voice assistant generates a screen2414 to confirm receipt of the voice command. At step seven, the homescreen 2416 is displayed.

As was mentioned above, a user 108 may use voice commands to cause thedelivery of a bolus of medicament. FIG. 25 illustrates a sequence ofscreens organized into eight steps for a voice-assisted bolus sequence.Initially, at screen 2500, the user has activated the use of voicecommands and submits a request 2502 to calculate a bolus using acarbohydrate value of 25 grams. At step two, the voice assistant inscreen 2504 acknowledges the voice command provided by the user 108. Atstep three, screen 2506 is displayed to illustrate how the application158 calculates the insulin bolus. The calculation is performed asdiscussed above. At step four, the voice assistant asks the user 108 toconfirm the bolus value that is calculated using voice commands oron-screen buttons (see message 2510 on screen 2508). After the user 108has confirmed the bolus value that was calculated in step four, thevoice assistant in screen 2512, as part of step five, asks the user 108to provide a confirmatory code to confirm delivery of the insulin bolus.In the example the user provides a pass code “1234” (see 2514). In stepsix, as indicated by screen 2516, the voice assistant provides anindication that the bolus has been confirmed with the proper pass code.In step seven, screen 2518 is displayed to indicate that the bolus is inprocess and specifies the bolus dosage. A status bar 2520 is displayedin the example shown. The user 108 may have the ability to cancel thebolus by selecting a cancellation button. Lastly, in step eight, uponsuccessful bolus delivery the system returns to a home screen 2522. Theinsulin on board value is updated to reflect the insulin bolus that hasbeen delivered.

The application 158 may use geo-location or geo-positioning information,such as GPS data, to aid in helping the user. The information may beused with a smartwatch 130 or a vehicle infotainment system. Forexample, in a vehicle infotainment system, as shown in FIG. 26, theapplication 158 may note that the user 108 is on a routine route wherethe user is on their way to exercise based on geolocation services. Avoice assistant then displays the message 2604 on screen 2602 that isshown on display 2600. The message 2604 notes that it appears that theuser is on the way to exercise, prompting the system to request of theuser if they would like to enter a mode of insulin delivery that issuitable for exercising to avoid an excursion in glucose level. The user108 may accept or reject the protective insulin delivery mode via voicecommand or via the touchscreen.

More generally, the application 158 may leverage geolocationinformation, such as GPS and map information, to assist the user 108. Asshown in FIG. 27, at 2702 in the flowchart 2700, the application mayreceive GPS information regarding the current location of the car anduser 108 via either the vehicle or via the management device 104. TheGPS information is compared to known GPS data at 2704 to see if there isa match. For example, the sequence of the GPS data may correspond to aroute that the user takes to a restaurant. The application 158 may thenask the user 108 if the user is going to eat and wished to shift to aninsulin delivery mode suitable for a meal. Similarly, the GPS data couldindicate instead that the car is no longer moving and corresponds to arestaurant location. The same prompt can be produced as before regardingwhether the user is eating. In general, the application may take actionif there is a location match that is associated with an action at 2706.Otherwise, no action is taken. The application 158 may also leverageother smartphone applications that have given permission to useinformation to make insulin controller decisions. For example, if a userdecides to order food and beverage via a mobile application orderingplatform, the application 158 may read relevant information such ascarbohydrates, calories, fat, or other values that may automatically beadded in the user's insulin management bolus calculation. The user maydecide to use this information immediately to deliver a bolus or delaytreatment based on a set time. If the bolus execution is delayed, thesystem will prompt the user to confirm bolus delivery once the timer hasexpired.

While exemplary embodiments have been described herein, various changesin form and detail may be made relative to the exemplary embodimentswithout departing from the intended scope of the attached claims.

1. A method performed by a processor of a smartwatch, comprising:displaying a user interface element on a display of the smartwatch torequest a bolus of medicament from a medicament delivery device;determining that the user interface element has been used to request abolus of medicament be delivered to a user of the medicament deliverydevice; and responsive to the determining, instructing the medicamentdelivery device to deliver the medicament bolus to the user.
 2. Themethod of claim 1, wherein the medicament includes at least one ofinsulin, a glucagon-like peptide-1 (GLP-1) agonist or pramlintide. 3.The method of claim 1, further comprising determining a dosage of thebolus of medicament for the user.
 4. The method claim 3, wherein thedetermining of the dosage comprises displaying a prompt on the displayof the smartwatch to obtain information for the determining of thedosage.
 5. The method of claim 4, wherein the prompt requests acarbohydrates quantity.
 6. The method of claim 1, further comprisingdisplaying a reminder of when the user should eat on the display of thesmartwatch.
 7. A method performed by a processor of a smartwatch havinga display, comprising: obtaining measured analyte history and medicamentdelivery history for the user; and displaying on the display at leastone of an indication of historical measured analyte values from themeasured analyte history and/or information about medicament deliveriesin the medicament delivery history.
 8. The method of claim 7, whereinthe medicament is insulin and the measured analyte values are glucoseconcentration values.
 9. The method of claim 7, further comprisingdisplaying a user interface element on the display for accessinginformation regarding a party under care of the user.
 10. The method ofclaim 7, further comprising detecting motion by the user and in responsedisplaying an option for the user to change a mode of operation toprotect the user.
 11. A method performed by a processor of a vehicleinfotainment system, comprising: displaying a user interface element ona display vehicle infotainment system of the to request a bolus ofmedicament from a medicament delivery device; determining that the userinterface element has been used to request a bolus of medicament bedelivered to a user of the medicament delivery device; and responsive tothe determining, instructing the medicament delivery device to deliverthe medicament bolus to the user.
 12. The method of claim 11, whereinthe medicament includes at least one of insulin, a glucagon-likepeptide-1 (GLP-1) agonist or pramlintide.
 13. The method of claim 11,further comprising determining a dosage of the bolus of medicament forthe user.
 14. The method claim 13, wherein the determining of the dosagecomprises outputting a prompt to obtain information for the determiningof the dosage.
 15. The method of claim 14, wherein the prompt requests acarbohydrates quantity.
 16. The method of claim 14, wherein the userprovides a spoken response to the prompt.
 17. A method performed by aprocessor of a vehicle infotainment system having a display, comprising:obtaining measured analyte history and medicament delivery history forthe user; and displaying on the display of the vehicle infotainmentsystem at least one of an indication of historical measured analytevalues from the measured analyte history and/or information aboutmedicament deliveries in the medicament delivery history.
 18. The methodof claim 17, wherein the medicament is insulin and the measured analytevalues are glucose concentration values.
 19. The method of claim 17,further comprising outputting alarms, alerts or notifications to theuser via the vehicle infotainment system.
 20. The method of claim 19,wherein the outputting comprises outputting the alarms, alerts ornotifications by displaying information on the display of the vehicleinfotainment system or by generating audio output.